Skip to content

Add bazel guide for maintainers#668

Open
shameekganguly wants to merge 1 commit intomasterfrom
shameek/bazel_dev
Open

Add bazel guide for maintainers#668
shameekganguly wants to merge 1 commit intomasterfrom
shameek/bazel_dev

Conversation

@shameekganguly
Copy link
Copy Markdown
Contributor

Add an unpublished guide on the bazel build system as it relates to Gazebo, targeted towards Gz package maintainers.

Signed-off-by: Shameek Ganguly <shameek@intrinsic.ai>
Copy link
Copy Markdown
Contributor

@iche033 iche033 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

looks good. We can either add this to index.yaml now or add it to the relevant section once #662 gets in

@shameekganguly
Copy link
Copy Markdown
Contributor Author

looks good. We can either add this to index.yaml now or add it to the relevant section once #662 gets in

I'd suggest we wait for #662 to land before publishing this guide.


**Uploading Gz Packages to BCR:**

Bazel modules for Gz packages can be uploaded to the Bazel Central Registry. This is achieved by manually triggering the **"Publish to BCR"** GitHub workflow from the GitHub UI, selecting a released tag as the input.
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I notice that in the following PRs, you've updated the Publish to BCR workflow to automatically open pull requests when stable tags are pushed (though I haven't yet seen a workflow triggered in this manner)

If we are planning to roll this out to all our packages, I recommend opening a tracking issue in https://github.com/gazebo-tooling/release-tools and keep @j-rivero in the loop

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Status: Inbox

Development

Successfully merging this pull request may close these issues.

4 participants